• Bump JS and Noir Aztec dependencies from v5.0.0-rc.1 to v5.0.0-rc.2.
• Update Noir contract instances to match renamed class-id field in rc.2.
• Adjust TS test utilities for updated Aztec address construction API.

graph TD
  A["package.json"] --> B[("Aztec JS packages\n@aztec/*")]
  A --> C[("Benchmark prerelease\ntgz")]
  D["Noir contracts\n(Nargo.toml)"] --> E[("aztec-packages\ngit tag rc.2")]
  F["Noir logic/tests"] --> D --> E
  G["TS test utils"] --> B
  subgraph Legend
    direction LR
    _cfg["Config / Manifest"] ~~~ _code["Code change"] ~~~ _ext[("External dependency")]
  end

Loading

The following are alternative approaches to this PR:

1. Use an npm-published benchmark version (semver) instead of a tarball URL

• ➕ Reproducible installs without relying on a specific GitHub release asset URL
• ➕ Cleaner dependency graph and lockfile diffs
• ➕ Better compatibility with tooling (audit, caching, registries)
• ➖ Requires publishing the prerelease to npm (or internal registry) first
• ➖ May slow down consumption of ad-hoc prereleases

2. Centralize Aztec version pinning via npm overrides/resolutions

• ➕ Single place to control Aztec versions across transitive deps
• ➕ Reduces risk of mixed rc.1/rc.2 sub-dependency graphs
• ➖ Does not help Noir (Nargo) dependencies
• ➖ Can mask incompatible transitive constraints and cause runtime surprises

3. Track aztec-packages by commit SHA instead of tag for Noir deps

• ➕ Maximum reproducibility (tags can be moved in rare cases)
• ➕ Enables pinning to a known-good commit if rc.2 tag has issues
• ➖ Harder to reason about compared to a public release tag
• ➖ More maintenance when updating versions

Recommendation: The PR’s approach (move everything to rc.2 and apply minimal compatibility fixes) is appropriate for an RC upgrade. The main improvement to consider is replacing the benchmark GitHub tarball dependency with an npm-published prerelease version when available to improve install reproducibility and tooling compatibility; otherwise, the current pin is acceptable as a temporary prerelease measure.

Bug fix (3) +4 / -3

logic.nrFix ContractInstance field rename for escrow instance derivation +1/-1

Fix ContractInstance field rename for escrow instance derivation

• Updates ContractInstance construction to use original_contract_class_id instead of contract_class_id, matching the rc.2 API/struct layout.

src/escrow_contract/src/library/logic.nr

utils.tsUse fromBigIntUnsafe for PRIVATE_ADDRESS constant +2/-1

Use fromBigIntUnsafe for PRIVATE_ADDRESS constant

• Updates the test constant construction to use AztecAddress.fromBigIntUnsafe, reflecting an API/validation change in the upgraded Aztec JS libraries.

src/ts/test/utils.ts

main.nrFix VaultDeployer ContractInstance field rename +1/-1

Fix VaultDeployer ContractInstance field rename

• Updates the deploy-time ContractInstance literal to set original_contract_class_id, matching the rc.2 struct field naming and fixing compilation.

src/vault_deployer/src/main.nr

Tests (2) +2 / -2

get_escrow.nrUpdate escrow test assertion for renamed class-id field +1/-1

Update escrow test assertion for renamed class-id field

• Adjusts test expectations to read original_contract_class_id instead of contract_class_id when validating the derived escrow ContractInstance.

src/escrow_contract/src/test/test_logic_contract/src/test/get_escrow.nr

utils.nrUpdate helper to return original_contract_class_id +1/-1

Update helper to return original_contract_class_id

• Aligns the test utility’s escrow class-id extraction with the rc.2 ContractInstance field rename.

src/escrow_contract/src/test/utils.nr

Other (9) +24 / -24

package.jsonBump Aztec JS deps to 5.0.0-rc.2 and update benchmark prerelease +11/-11

Bump Aztec JS deps to 5.0.0-rc.2 and update benchmark prerelease

• Updates the package version and Aztec-related dependencies from rc.1 to rc.2. Switches the benchmark dependency to a specific rc.2 prerelease tarball URL and updates the internal aztecVersion config.

package.json

Nargo.tomlPin dripper Noir dependency to aztec-packages v5.0.0-rc.2 +1/-1

Pin dripper Noir dependency to aztec-packages v5.0.0-rc.2

• Updates the Aztec Noir dependency tag from v5.0.0-rc.1 to v5.0.0-rc.2 to align contract compilation with the new release candidate.

src/dripper/Nargo.toml

Nargo.tomlUpgrade escrow Noir deps (aztec + serde) to v5.0.0-rc.2 +2/-2

Upgrade escrow Noir deps (aztec + serde) to v5.0.0-rc.2

• Bumps both the Aztec Noir library and the serde crate references to the v5.0.0-rc.2 tag to match Aztec rc.2 breaking changes.

src/escrow_contract/Nargo.toml

Nargo.tomlPin escrow test contract to aztec-packages v5.0.0-rc.2 +1/-1

Pin escrow test contract to aztec-packages v5.0.0-rc.2

• Updates the test contract’s Aztec dependency tag from rc.1 to rc.2 to ensure tests compile against the upgraded Noir libraries.

src/escrow_contract/src/test/test_logic_contract/Nargo.toml

Nargo.tomlPin generic_proxy Noir dependency to aztec-packages v5.0.0-rc.2 +1/-1

Pin generic_proxy Noir dependency to aztec-packages v5.0.0-rc.2

• Updates the Aztec Noir dependency tag to v5.0.0-rc.2 for the generic proxy contract.

src/generic_proxy/Nargo.toml

Nargo.tomlUpgrade nft_contract Noir deps (aztec + compressed_string) to rc.2 +2/-2

Upgrade nft_contract Noir deps (aztec + compressed_string) to rc.2

• Bumps Aztec and compressed_string Noir dependencies to v5.0.0-rc.2 to keep the NFT contract compatible with the upgraded Aztec toolchain.

src/nft_contract/Nargo.toml

Nargo.tomlUpgrade token_contract Noir deps to rc.2 +4/-4

Upgrade token_contract Noir deps to rc.2

• Updates Aztec, uint_note, balance_set, and compressed_string dependency tags to v5.0.0-rc.2 to align with the Aztec rc.2 ecosystem.

src/token_contract/Nargo.toml

Nargo.tomlPin vault_contract Noir dependency to aztec-packages v5.0.0-rc.2 +1/-1

Pin vault_contract Noir dependency to aztec-packages v5.0.0-rc.2

• Updates the vault contract’s Aztec Noir dependency tag to v5.0.0-rc.2 for compatibility with the new RC.

src/vault_contract/Nargo.toml

Nargo.tomlPin vault_deployer Noir dependency to aztec-packages v5.0.0-rc.2 +1/-1

Pin vault_deployer Noir dependency to aztec-packages v5.0.0-rc.2

• Updates the vault deployer contract’s Aztec Noir dependency tag from rc.1 to rc.2.

src/vault_deployer/Nargo.toml

Description

package.json now depends on @defi-wonderland/aztec-benchmark via a GitHub release tarball URL, which
is less registry-standard and can be harder to mirror/cache in some environments. Since the package
is only referenced by benchmark code and the bench script, keeping it in runtime dependencies forces
all consumers to download it unnecessarily.

Code

package.json[37]

+    "@defi-wonderland/aztec-benchmark": "https://github.com/defi-wonderland/aztec-benchmark/releases/download/prerelease-a2add93/defi-wonderland-aztec-benchmark-5.0.0-rc.2-prerelease.a2add93.tgz",

Evidence

The PR switches the aztec-benchmark dependency to a GitHub tarball URL under runtime dependencies,
while repository usage shows it’s only imported by benchmark code and invoked via the bench script,
indicating it doesn’t need to be installed for normal consumption of the package.

package.json[11-40]
benchmarks/token_contract.benchmark.ts[8-13]
benchmarks/escrow_contract.benchmark.ts[8-19]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`@defi-wonderland/aztec-benchmark` is a GitHub tarball URL under `dependencies`, which impacts downstream consumers (extra install surface + URL-based fetch).

### Issue Context
The dependency is only used by benchmark sources and the `bench` script, not by library runtime code.

### Fix Focus Areas
- package.json[28-51]

### Suggested fix
1. Move `@defi-wonderland/aztec-benchmark` from `dependencies` to `devDependencies`.
2. Prefer a registry-published version (e.g., `5.0.0-rc.2`) when available; if a tarball is required temporarily, consider documenting why and how it’s pinned/released so consumers understand the provenance expectations.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools